Royal Borough of Kingston upon Thames

Tree preservation zone

There is a problem

• 1000 entries must have dates in YYYY-MM-DD format

entity: 19207107

• reference: 1026
• tree-preservation-order: Multiple Properties Chessington
• tree-preservation-zone-type: group
• geometry: MULTIPOLYGON (((-0.304506 51.367448,-0.304482 51.367454,-0.304472 51.367459,-0.304457 51.367472,-0.304453 51.367480,-0.304453 51.367496,-0.304456 51.367504,-0.304462 51.367511,-0.304480 51.367523,-0.304491 51.367527,-0.304516 51.367530,-0.304529 51.367530,-0.304553 51.367524,-0.304572 51.367513,-0.304578 51.367506,-0.304584 51.367490,-0.304583 51.367482,-0.304579 51.367474,-0.304573 51.367467,-0.304565 51.367460,-0.304556 51.367455,-0.304544 51.367451,-0.304532 51.367449,-0.304506 51.367448)))
• point: POINT (-0.304518 51.367489)
• entry-date: 2023-06-30
• start-date:

  start-date must be a real date

How to fix this issue

Your data is missing a start-date.

The tree preservation zone guidance explains how to fix the issue:

start-date

The date that the tree preservation order came into force, written in YYYY-MM-DD format.

Example: 1984-03-28

How to improve Royal Borough of Kingston upon Thames’s data

1. Fix the errors indicated
2. Use the check service to make sure the data meets the standard
3. Publish the updated data on the endpoint URL